🪲 [Fix]: Wildcard maximum versions no longer fail module processing - #446
Merged
Marius Storhaug (MariusStorhaug) merged 6 commits intoAug 8, 2026
Merged
Conversation
Marius Storhaug (MariusStorhaug)
changed the title
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Marius Storhaug (MariusStorhaug)
marked this pull request as ready for review
August 8, 2026 15:20
Marius Storhaug (MariusStorhaug)
requested a review
from a team
as a code owner
August 8, 2026 15:20
Marius Storhaug (MariusStorhaug)
deleted the
fix-wildcard-maximumversion
branch
August 8, 2026 15:27
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Module requirements can now use wildcard maximum versions such as
1.*without module builds or installations failing. Versions remain constrained to the requested major or minor release line, while concrete maximum versions keep their existing behavior.Fixed: wildcard maximum versions no longer fail module builds
Module manifests can now preserve wildcard maximum-version requirements instead of rejecting them as invalid version values. A requirement such as
MaximumVersion = '1.*'remains usable during manifest generation.Fixed: wildcard maximum versions resolve to the correct release range
Module installation translates wildcard maximum versions into an exclusive upper bound. For example,
MinimumVersion = '1.0.0'andMaximumVersion = '1.*'resolve to the range[1.0.0,2.0.0), allowing 1.x releases without admitting 2.x releases. Unsupported wildcard patterns are reported clearly.Technical details
1.*to the exclusive upper bound2.0.0and1.2.*to1.3.0; concrete maximum versions remain inclusive.ThreadJobrequirement withModuleVersion = '1.0.0'andMaximumVersion = '1.*'.main; the repository's native Zensical workflow remains unchanged and continues to build directly fromzensical.toml..github/actions/**(PowerShell)tests/**(PowerShell)Relevant issues (or links)